Corrected Node 20 References #127518
Corrected Node 20 References #127518
Conversation
The incorrect CLI command was given for upgrading to Node 20 on Linux, showing the command to upgrade to Node 22 while stating this would set it to Node 20. For Windows, it showed the command to upgrade to Node 20 and stated this would set it to Node 22.
|
@DameonL : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 320145d: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
I'm checking with @MadhuraBharadwaj-MSFT who recently made the update that this PR is trying to revert. |
|
Since Node 22 is supported now, this PR may need to be replaced with one that consistently updates the docs to refer to Node 22 and provides instructions to update to 22, and removes references to Node 20. |
|
@DameonL the trouble with specifying any version number is that you have to eventually go back and update it as the lang stack rolls ever forward 😏 |
|
@DameonL There was a mismatch there, so thanks for highlighting it. Madhura is fixing it in favor of Node.js 22 rather than 20, but thanks again for your help, and sorry we couldn't use your contribution. Please feel free to suggest more docs fixes in the future! |
The incorrect CLI command was given for upgrading to Node 20 on Linux, showing the command to upgrade to Node 22 while stating this would set it to Node 20. For Windows, it showed the command to upgrade to Node 20 and stated this would set it to Node 22. Setting the Node version to 22 will break some Functions apps.